Systems and methods to automatically join conference

ABSTRACT

Systems and methods are described to enable a device of a user to automatically join an ongoing conference, where the device is not currently joined to the conference. A first audio signature is generated based on voices of users already in the conference, and a second audio signature is generated based on an audio signal captured by a microphone of the device associated with the first user when the device associated with the first user was not joined to the conference. The first audio signature and the second audio signature are compared, and in response to determining that first audio signature matches the second audio signature, the device associated with the first user is joined to the conference.

BACKGROUND

This disclosure is directed to enabling a device of a user toautomatically join an ongoing conference, where the device is notcurrently joined to the conference. In particular, such a device isenabled to join the conference based on whether an audio signatureassociated with a plurality of voices of users already in the conferencematches an audio signature generated based on an audio signal capturedby a device associated with the user.

SUMMARY

Advancements in communication technology have improved the ability ofusers to communicate (e.g., such as via video conferencing) withcolleagues, family and friends located in a different physical locationthan the user. For example, conferencing systems (e.g., MicrosoftTeams™, Zoom™, etc.) are often used to enable colleagues in separate,geographically distributed physical locations to have a face-to-faceconversation via a video conference. In some circumstances, multipledevices in a single location may be joined to a conference (e.g., in aphysical conference room at an office), and other users in differentgeographical locations may also be participating in the conference overa network. However, having multiple devices joined to a conference inthe same physical location may cause several issues. For example, audiofeedback (e.g., a high-pitched screech or squeal) may be created if asignal received by a microphone of one of the devices is fed to aspeaker, and such signal is output by the speaker and again received bythe microphone. Such audio feedback can be distracting and irritating tousers participating in the conference. In addition, although a user maybe present at the conference, it may be the case that the user is in aconference room with multiple users participating in the conference viaa single device joined to the conference. In this situation, otherconference participants may be unaware the user is participating in theconference (e.g., if an icon associated with the user is not presentedon a display associated with the conference call). Moreover, there mayno record of the user having participated in the conference.

In one approach, a user may manually select an option to join aconference and select a mute option presented on a display of his or herdevice, in order to avoid audio feedback. However, this may beburdensome for the user. In particular, the user may not know aconference ID that may be required to join the conference. Additionally,there may be a delay between joining the conference and the audio beingmuted. In this circumstance, other users may be subjected to undesirableaudio feedback while the user is attempting to mute his or her device.Alternatively, the user may decide not to bring his or her device to theconference room, and thus other users joined to the conference (e.g.,over the network and not present in the conference room) may notrecognize that the user is participating in the conference.

To overcome these problems, systems and methods are provided herein forautomatically joining a device associated with a first user to aconference of a plurality of users when the user is proximate to anotherdevice already joined to the conference. A conferencing server maygenerate (and store) a first audio signature based on voices of theplurality of users already in the conference. Later, a new device thatis not joined to the conference attempts to join the conference and maycapture a sample of ambient sounds using a microphone. In someembodiments, the new device locally generates a second audio signaturebased on the ambient sample and transmits the second audio signature tothe server. In some embodiments, the new device sends the ambient soundsto the conferencing server, allowing the server to generate the secondsignature. In response to determining that first audio signature matchesthe second audio signature, the device associated with the first user isjoined to the conference.

In some aspects of the disclosure, the audio signal captured by themicrophone of the device associated with the first user comprises atleast one of the voices of the plurality of users in the conference. Forexample, a conferencing application may determine whether the deviceassociated with the first user is in a same physical location as adevice associated with at least one user of the plurality of users inthe conference, and the audio signal captured by the microphone of thedevice associated with the first user may be captured in response todetermining that the device associated with the first user is in a samephysical location as the device associated with the at least one user.In some embodiments, the device may attempt to join in response to arequest (e.g., via a user interface) to join a conference. For example,the user may say “Join current conference,” or click or touch a buttonlabeled “Join current conference.”

The joining of the device associated with the first user to theconference may comprise generating for presentation an icon indicatingto each user joined to the conference that the first user is joined tothe conference. In this way, other users participating in the conference(e.g., over the network and not present in a conference room with thefirst user) may be made aware that the user is participating in theconference. In addition, after the device associated with the first useris joined to the conference, the conferencing application may cause themicrophone and a speaker of the device associated with the first user tobe automatically muted without receiving a user command to mute themicrophone and the speaker. Accordingly, audio feedback that may bedistracting and irritating to users in the conference can be avoided.

In some aspects of the disclosure, the conferencing server may assign aconference identifier to the conference, and associate a first audiosignature with the conference identifier, and joining the deviceassociated with the first user to the conference may comprisetransmitting the conference identifier to the device associated with thefirst user.

In some embodiments, the first audio signature and the second audiosignature are generated by sampling the voices of the plurality of usersin the conference and the audio signal captured by the microphone,respectively, at regular intervals. The first audio signature and thesecond audio signature may also be generated by transcribing the voicesof the plurality of users in the conference and the audio signalcaptured by the microphone, respectively, into text.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects and advantages of the present disclosurewill be apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings, inwhich like reference characters refer to like parts throughout, and inwhich:

FIG. 1 shows an example of joining a device associated with a user to aconference, in accordance with some embodiments of this disclosure;

FIG. 2 shows an example of generating an audio signature, in accordancewith some embodiments of this disclosure;

FIG. 3 shows an example of a user entering a conference room in whichusers are participating in a conference, in accordance with someembodiments of this disclosure;

FIG. 4 is a diagram of illustrative conferencing devices, in accordancewith some embodiments of this disclosure;

FIG. 5 is a diagram of an illustrative conferencing system, inaccordance with some embodiments of this disclosure;

FIG. 6 is a flowchart of a detailed illustrative process for joining adevice associated with a user to a conference, in accordance with someembodiments of this disclosure; and

FIG. 7 is a flowchart of a detailed illustrative process for joining adevice associated with a user to a conference, in accordance with someembodiments of this disclosure.

DETAILED DESCRIPTION

FIG. 1 shows an example 100 of joining a device associated with user 106to conference 105. In some embodiments, a conferencing application joinsusers to a video and/or audio conference to enable communication withother users over a network. For example, the conferencing applicationjoins a device associated with user 102, and a device associated withuser 104, to conference 105), and users 102 and 104 may be located indifferent geographical locations (e.g., user 102 may be present inconference room 101 located in New York, while user 104 may be presentin conference room 103 located in California). Once users 102 and 104join the conference, the conferencing application may enable the usersto communicate with one another (e.g., via audio, video and/or textmessage) using one or more digital devices. The voices 107 of users 102and 104 may be detected (e.g., by respective microphones of conferencingdevices located in conference rooms 101 and 103), and the conferencingapplication may generate (e.g., locally or at a conferencing server) anaudio signature based on such detected voices. The generated audiosignatures may be stored at the conferencing server (e.g., server 508 inFIG. 5) in association with a conference ID. The signature may begenerated using a suitable voice processing technique (e.g., asdescribed in FIG. 2).

The conferencing application may then determine that user 106 (whosedevice is not yet joined to the conference), associated with device 110(e.g., a mobile device held by the user 106, and running theconferencing application), has physically entered conference room 103(or otherwise became proximate to conference Room 103), in which user104 is already participating in conference 105. Such determination maybe performed in any suitable manner (e.g., as discussed in more detailin FIG. 3). Once the conferencing application determines that user 106has entered conference room 103, microphone 113 of device 110 associatedwith user 106 may be triggered to begin detecting ambient audio. Forexample, the microphone 113 may detect the voices of user 102 (e.g.,over the network) and user 104 (e.g., in person in conference room 103)participating in the conference, and sample the detected voices of user102 and user 104. The conferencing application may generate (e.g.,locally or at a conferencing server) an audio signature 116 based on thedetected ambient audio signal 114. The conferencing server may receivethe generated audio signature 116, and the conferencing application maycompare audio signature 116 to the generated audio signature 108. If theconferencing application determines that audio signature 116 matchesaudio signature 108, device 110 of user 106 may be joined to conference105, to enable the user 106 to communicate over the network with user102, located in a different physical location from user 106. In someembodiments, the microphone of device 110 may be automatically muted(e.g., without receiving further user input), after device 110 of user106 is joined to conference 105, thereby minimizing or avoiding audiofeedback. If the conferencing application determines that audiosignature 116 does not match audio signature 108, the conferencingapplication may determine that user 106 should not be joined toconference 105. This may be advantageous for various reasons (e.g., toavoid joining a device of a user to the conference in a circumstancewhere the user may have happened to walk by a conference room but didnot intend to (or was not invited to) join the conference, therebyconserving network and/or device resources).

In some embodiments, the microphone 113 of the device 110 may betriggered in response to the conferencing application receiving arequest to join from the user (e.g., via a selectable option on a userinterface of the device, via voice command, etc.). For example, theconferencing application may detect that a new device (e.g., device 110)is attempting to join the conference 105, and the conferencingapplication may trigger a microphone of a device (e.g., a deviceassociated with user 102) of a user known to be joined to theconference, as well as the microphone of the device attempting to jointhe conference. The conferencing application may generate audiosignatures based on the captured audio of the microphone 113 of thedevice 110 and the captured audio of the device associated with user102, and join the device 110 to the conference 105 upon determining theaudio signatures match.

FIG. 2 shows an exemplary process of generating an audio signature. Asreferred to herein, the term “audio signature” or “audio fingerprint”may refer to any kind of a digital or analog representation of a sound.The audio signature may be a digital measure of certain acousticproperties that is deterministically generated from an audio signal andmay be used to identify an audio sample and/or quickly locate similaritems in an audio database. For example, an audio signature may be afile, data, or data structure that stores time-domain sampling of anaudio input. In another example, an audio signature may be a file, data,or data structure that stores a frequency-domain representation (e.g., aspectrogram) of an audio input. Exemplary generation of audio signaturesis described in greater detail in Blake et al., U.S. Patent ApplicationPublication No. 2019/0391788 A1, filed Jun. 26, 2018; Sanchez et al.,U.S. Patent Application Publication No. 2020/0186893 A1, filed Feb. 12,2020; Khan et al., U.S. Pat. No. 7,853,344, issued Dec. 14, 2010; andBogdanov, U.S. Pat. No. 7,451,078, issued Nov. 11, 2008, which arehereby incorporated by reference herein in their entireties.

As shown in FIG. 2, microphone 204 may receive audio input 202 (e.g., avoice of a user in the conference, background noise, music, recordedaudio, and/or other suitable audio signals), and convert audio input 202into an electrical signal. The detected audio input 202 may includefrequencies in a range of 20 Hz to 20 kHz (e.g., the sound wavefrequency that may be heard by the human ear). In some embodiments,audio input 202 may be sampled at regular intervals (e.g., periods of1-2 seconds with samples taken every few milliseconds during theperiod). For example, audio input 202 may be various segments of theaudio of the conference. The electrical signal output by the microphone204 may be an analog output, and may be digitized at digital signalprocessor 206 to facilitate further processing. In some embodiments, themicrophone 204 may be a MEMS microphone with a digital output.

The digital signal processor 206 (e.g., included in a general-purposemicroprocessor or a specialized digital signal processor) may performvarious operations on the received digital signal. In some embodiments,the digital signal processor 206 may perform a fast Fourier transformoperation on time-domain samples of the audio to produce afrequency-domain representation of the audio. In some embodiments, thedigital signal processor 206 may employ audio compression techniques, toreduce network resources and/or computing power to process the signal.In some embodiments, noise reduction techniques may be employed (e.g.,in a pre-processing stage) to filter out unwanted signals.

The generated audio signature 208 may comprise a time-domain and/orfrequency-domain representation (e.g., a spectrogram) of the signal. Insome embodiments, the device (e.g., device 110 of FIG. 1) associatedwith the user (e.g., user 106 of FIG. 1) may transmit an encodedtime-domain representation of the signal to a server and receive anddecode a frequency-domain representation of the signal. In someembodiments, digital signal processing including frequency analysis,peak volume detecting, audio hashing, waveform matching, and/or anyother digital signal processing method known to those skilled in the artmay be used to generate an audio signature. As another example, theaudio signature may comprise an audio signature or hash calculationdeterministically generated from a predefined portion of the audiosignal.

In some embodiments, the conferencing application may generate afeatures vector based on the output of the digital signal processor 206,and audio signature 208 may correspond to such features vector. Forexample, the features vector may comprise a sequence of valuesrepresenting various audio or acoustic features or characteristics(e.g., amplitude, modulation, tone, frequency, volume, speed, etc.) ofthe signal. Audio processing circuitry may analyze audio characteristicsof the signal to identify audio signatures using any suitable audioanalysis technique (e.g., frequency analysis to determine a basefrequency and unique harmonic pattern of a particular voice, phonemeanalysis to determine an accent of a particular voice, etc.). Forexample, the wave amplitude of the audio signal may be used to determinethe volume of the voice of user 202 and/or analyze frequency data todetermine the pitch and tone of the voice search query. The audioprocessing circuitry may also identify non-vocal audio such as music,sound effects, and the like using similar frequency analysis techniquesor any other suitable method of audio analysis. The identified audiocharacteristics may be stored in association with a timestamp of whenthe audio signal was received. Audio signal processing is discussed inmore detail in U.S. patent application Ser. No. 16/553,410, filed Aug.28, 2019, which is hereby incorporated by reference herein in itsentirety.

In some embodiments, the audio signal may be converted to transcribedtext, and such text may be used to generate audio signature 208. Forexample, the conferencing application may transcribe the audio responseinto a string of text (e.g., by any suitable automatic speechrecognition technique), or transcription of the audio signal may beachieved by external transcription services (e.g., Amazon Transcribe byAmazon, Inc. of Seattle, Wash. and Google Speech-to-Text by Google, Inc.of Mountain View, Calif.). The transcription of audio is discussed inmore detail in U.S. patent application Ser. No. 16/397,004, filed Apr.29, 2019, which is hereby incorporated by reference herein in itsentirety.

FIG. 3 shows an example of joining a user 310 to an ongoing conference301. Users 306, 308 are depicted as physically present in conferenceroom 300, and each of users 306 and 308 are already joined to theconference and communicating via conferencing device 302 with otherconference participants located in different physical locations. Theconferencing device 302 may include a camera and a microphone tofacilitate communication between the users present in conference room300 and users located in other physical locations (e.g., users 314, 316,318). In some embodiments, the conferencing application may display avideo feed of such users 314, 316, 318 at projector screen 304, and/oricons 312 for each user, to indicate which users are participating inthe conference. The conferencing application may also display a videofeed of the conference room 300 to users 314, 316 and 318 in theirrespective locations via their respective devices, and the video feed ofthe users 314, 316 and 318 (and the conference room 300) may also bepresented on projector screen 304.

When the user 310 enters conference room 300, the conferencingapplication (e.g., running at least in part on device 311 associatedwith the user 310) may activate the microphone of device 311 to capturesound in the conference room 300. For example, in order to optimallyutilize network and/or device resources, it may be desirable for theconferencing application to be activated (e.g., begin sampling ambientaudio) only upon determining the user has entered a physical conferenceroom where devices associated with the conference are located. Theconferencing application may determine that the user 310 has entered theconference room 300 using any suitable method.

In some embodiments, the conferencing application may determine that theuser has entered the conference room 300 based on GPS data retrievedfrom device 311, or based on an IP address associated with device 311,to determine the user's geographic location. For example, theconferencing application may compare GPS coordinates associated withdevice 311 to GPS coordinates or IP address information associated withdevices currently joined to the conference (e.g., stored at aconferencing server). If the comparison indicates that the user 310 isin the same location as device 302 (e.g., within a predeterminedthreshold distance, such as 10-20 feet), the conferencing applicationmay determine that the user 310 has entered conference room 300. Asanother example, the conferencing application may determine whetherdevice 311 is within a threshold distance of device 302 based on awireless signal strength between the devices (e.g., polling nearbydevices). For example, the conferencing application may determine arelative received signal strength indicator (RSSI) of a wireless signalbetween device 311 and the conferencing device 302, and based on theRSSI, an estimated distance between device 311 and device 302 (e.g.,using a lookup table that returns distance as a function of RSSI). Inanother example, the conferencing application may measure received radiofrequency (RF) power over a shared wireless signal to estimate alocation of the user. As another example, the conferencing applicationmay employ any suitable computer vision or facial recognition techniques(e.g., on an image or video feed of a camera of a device already joinedto an ongoing conference or of a device not yet joined to theconference) to recognize a user to be added to an ongoing conference.

In some embodiments, the conferencing application may determine that theuser has entered the conference room 300 by polling other devices joinedto the conference, to determine whether the user 310 and device 311 arein the vicinity of a threshold number of devices (e.g., five devices)joined to the conference. As another example, the conferencingapplication may monitor a smart lock or an RFID chip in the user'smobile phone to determine whether the user has entered a conference roomor physical location where conference participants are located. In someembodiments, the conferencing system may monitor the location of device311 during the conference, and upon determining that device 311 has leftthe conference room 300, may automatically remove the user 310 from theconference (and remove any indicators that the user is stillparticipating in the conference). In some embodiments, a selectableoption on the device 311 may be selected by the user 310 to attempt tojoin the current conference (e.g., conference 301). The conferencingapplication may then confirm that the device 311 is within apredetermined proximity to other devices participating in the conference(e.g., prior to triggering microphones of the devices to capture audio,and generating audio signatures based on the captured audio).

When the conferencing application determines that device 311 associatedwith user 310 has entered the conference room 300, the microphone ofdevice 311 may be activated to sample ambient audio in the conferenceroom 300. It should be noted that the determination may be based onproximity to other devices joined to the conference, and may not be roomrelated or based on entering a particular room. In some embodiments, themicrophone may be configured to capture audio of only the users withinthe conference room 300 where device 311 is located, or alternativelycapture audio of both the conference room 300 and audio over the network(e.g., received from one or more devices associated with users 314, 316,318). As discussed in connection with FIG. 1, and as discussed in moredetail below, the conferencing application (e.g., at device 311 or at aconferencing server) may generate an audio signature based on theambient audio detected by device 311, and may join the user to theconference upon determining that such generated audio signature matchesaudio signatures stored at the conferencing server (e.g., and which areassociated with a conference ID of the conference). In some embodiments,when the user 310 is joined to the conference, the conferencingapplication may cause the microphone, camera and/or speaker of device311 to be automatically muted and/or disabled, to avoid subjecting otherconference participant's to audio feedback, and may cause the display ofan icon on projector 304 indicating to all conference participants thatthe user 310 is now participating in the conference.

FIG. 4 shows generalized embodiments of illustrative conferencingdevices 400 and 401. Any of the devices discussed in connection withFIGS. 1-3 may be implemented as conferencing devices 400 or 401. Theconferencing application may be executed on any combination ofconferencing device 400 and/or device 401 (e.g., locally) and/orconferencing server 508 (e.g., remotely) of FIG. 5, and the stepsillustrated in FIGS. 1-3 may be performed by the conferencingapplication locally or remotely. As depicted, conferencing device 400may be a smartphone or tablet, whereas conferencing device 401 may be aconferencing system that includes equipment device 416 (e.g., a PC,set-top box, CPU, video-game console, etc.). Conferencing devices 400and 401 may receive content and data via input/output (hereinafter“I/O”) path 402 (e.g., I/O circuitry). I/O path 402 may provide content(e.g., Internet content, content available over a local area network(LAN) or wide area network (WAN), and/or other content) and data tocontrol circuitry 404, which includes processing circuitry 406 andstorage 408. Control circuitry 404 may be used to send and receivecommands, requests, and other suitable data using I/O path 402. I/O path402 may connect control circuitry 404 (and specifically processingcircuitry 406) to one or more communications paths (described below).I/O path 402 may additionally provide circuitry to control userinterface 410. I/O functions may be provided by one or more of thesecommunications paths but are shown as a single path in FIG. 4 to avoidovercomplicating the drawing.

Control circuitry 404 may be based on any suitable processing circuitrysuch as processing circuitry 406. As referred to herein, processingcircuitry should be understood to mean circuitry based on one or moremicroprocessors, microcontrollers, digital signal processors,programmable logic devices, field-programmable gate arrays (FPGAs),application-specific integrated circuits (ASICs), etc., and may includea multi-core processor (e.g., dual-core, quad-core, hexa-core, or anysuitable number of cores) or supercomputer. In some embodiments,processing circuitry may be distributed across multiple separateprocessors or processing units, for example, multiple of the same typeof processing units (e.g., two Intel Core i7 processors) or multipledifferent processors (e.g., an Intel Core i5 processor and an Intel Corei7 processor). In some embodiments, control circuitry 404 executesinstructions for a conferencing system stored in memory (e.g., storage408). Specifically, control circuitry 404 may be instructed by theconferencing system to perform the functions discussed above and below.

In client-server-based embodiments, control circuitry 404 may includecommunications circuitry suitable for communicating with a conferencingsystem server (e.g., server 508 of FIG. 5) or other networks or servers.The instructions for carrying out the above-mentioned functionality maybe stored on a server. Communications circuitry may include a cablemodem, an integrated service digital network (ISDN) modem, a digitalsubscriber line (DSL) modem, a telephone modem, Ethernet card, or awireless modem for communications with other equipment, or any othersuitable communications circuitry. Such communications may involve theInternet or any other suitable communications networks or paths. Inaddition, communications circuitry may include circuitry that enablespeer-to-peer communication of conferencing devices, or communication ofconferencing devices in locations remote from each other.

As referred to herein, the phrase “conferencing device” and “userdevice” should be understood to mean any device for accessing thecontent described above, such as a television, a Smart TV, a set-topbox, an integrated receiver decoder (IRD) for handling satellitetelevision, a digital storage device, a digital media receiver (DMR), adigital media adapter (DMA), a streaming media device, a personalcomputer (PC), a laptop computer, a tablet, a WebTV box, a smart phone,or any other television equipment, computing equipment, or wirelessdevice, and/or combination of the same.

Memory may be an electronic storage device provided as storage 408 thatis part of control circuitry 404. As referred to herein, the phrase“electronic storage device” or “storage device” should be understood tomean any device for storing electronic data, computer software, orfirmware, such as random-access memory, read-only memory, hard drives,optical drives, digital video disc (DVD) recorders, compact disc (CD)recorders, BLU-RAY disc (BD) recorders, BLU-RAY 3D disc recorders,digital video recorders (DVRs, sometimes called personal videorecorders, or PVRs), solid state devices, quantum storage devices,gaming consoles, gaming media, or any other suitable fixed or removablestorage devices, and/or any combination of the same. Nonvolatile memorymay also be used (e.g., to launch a boot-up routine and otherinstructions). Cloud-based storage, described in relation to FIG. 5, maybe used to supplement storage 408 or instead of storage 408.

Control circuitry 404 may include audio circuitry, video circuitry, andtuning circuitry, such as one or more analog tuners, one or more MP4decoders or other digital decoding circuitry, or any other suitabletuning or audio circuits or combinations of such circuits. Encodingcircuitry (e.g., for converting over-the-air, analog, or digital signalsto audio signals for storage) may also be provided. Control circuitry404 may also include scaler circuitry for upconverting anddownconverting content into the preferred output format of theconferencing device 400. Circuitry 404 may also includedigital-to-analog converter circuitry and analog-to-digital convertercircuitry for converting between digital and analog signals. The tuningand encoding circuitry may be used by the conferencing device to receiveand to display, to play, or to record content. The tuning and encodingcircuitry may also be used to receive guidance data. The circuitrydescribed herein, including, for example, the tuning, audio-generating,encoding, decoding, encrypting, decrypting, scaler, and analog/digitalcircuitry, may be implemented using software running on one or moregeneral purpose or specialized processors. Multiple tuners may beprovided to handle simultaneous tuning functions. If storage 408 isprovided as a separate device from user device 400, the tuning andencoding circuitry (including multiple tuners) may be associated withstorage 408.

A user may send instructions to control circuitry 404 using user inputinterface 410. User input interface 410 may be any suitable userinterface, such as a remote control, mouse, trackball, keypad, keyboard,touchscreen, touchpad, stylus input, joystick, voice recognitioninterface, or other user input interfaces. Display 412 may be atouchscreen or touch-sensitive display. In such circumstances, userinput interface 410 may be integrated with or combined with display 412.Display 412 may be provided as a stand-alone device or integrated withother elements of each one of conferencing device 400 and device 401.Speakers 414 may be provided as integrated with other elements of eachof conferencing device 400 and device 401. In the case of conferencingdevice 401, speakers 414 may be stand-alone units (e.g., smartspeakers). The audio component of videos and other content displayed ondisplay 412 may be played through speakers 414. In some embodiments, theaudio may be distributed to a receiver (not shown), which processes andoutputs the audio via speakers 414.

The conferencing application may be implemented using any suitablearchitecture. For example, it may be a stand-alone application whollyimplemented on conferencing device 400 and/or 401. In such an approach,instructions of the application are stored locally (e.g., in storage408), and data for use by the application is downloaded on a periodicbasis (e.g., from an out-of-band feed, from an Internet resource, orusing another suitable approach). Control circuitry 404 may retrieveinstructions of the application from storage 408 and process theinstructions to generate any of the displays discussed herein. Based onthe processed instructions, control circuitry 404 may determine whataction to perform when input is received from input interface 410. Forexample, movement of a cursor on a display up/down may be indicated bythe processed instructions when input interface 410 indicates that anup/down button was selected.

In some embodiments, the conferencing application is aclient/server-based application. Data for use by a thick or thin clientimplemented on device 400 or device 401 may be retrieved on-demand byissuing requests to a server (e.g., conferencing server 508 of FIG. 5)remote to the device 400 or device 301. In one example of aclient/server-based conferencing application, control circuitry 404 runsa web browser that interprets web pages provided by a remote server(e.g., conferencing server 508). For example, the remote server maystore the instructions for the application in a storage device. Theremote server may process the stored instructions using circuitry (e.g.,control circuitry 404) and generate the displays discussed above andbelow. The user device may receive the displays generated by the remoteserver and may display the content of the displays locally on device 400or device 401. This way, the processing of the instructions is performedremotely by the server while the resulting displays are provided locallyon device 400 or device 401. Device 400 or device 401 may receive inputsfrom the user via input interface 410 and transmit those inputs to theremote server for processing and generating the corresponding displays.For example, on device 400 or device 401 may transmit a communication tothe remote server indicating that an up/down button was selected viainput interface 410. The remote server may process instructions inaccordance with that input and generate a display of the applicationcorresponding to the input (e.g., a display that moves a cursorup/down). The generated display is then transmitted to device 400 ordevice 401 for presentation to the user.

In some embodiments, the conferencing application is downloaded andinterpreted or otherwise run by an interpreter or virtual machine (runby control circuitry 404). In some embodiments, the application may beencoded in the ETV Binary Interchange Format (EBIF), received by controlcircuitry 404 as part of a suitable feed, and interpreted by a useragent running on control circuitry 404. For example, the application maybe an EBIF application. In some embodiments, the guidance applicationmay be defined by a series of JAVA-based files that are received and runby a local virtual machine or other suitable middleware executed bycontrol circuitry 404. In some of such embodiments (e.g., thoseemploying MPEG-2 or other digital media encoding schemes), theapplication may be, for example, encoded and transmitted in an MPEG-2object carousel with the MPEG audio and video packets of a program.

Conferencing device 400 and conferencing device 401 of FIG. 4 can beimplemented in system 500 of FIG. 5 as any combination of conferencingdevice 502, conferencing device 505, or conferencing device 506.Conferencing devices, on which a conferencing system may be implemented,may function as stand-alone devices or may be part of a network ofdevices. Conferencing server 508 may have a similar configuration toconferencing device 401, although conferencing server 508 may notinclude certain elements (e.g., a display, a user interface, speakers,etc.). Various network configurations of devices may be implemented andare discussed in more detail below.

In system 500, there may be multiple conferencing devices, but onlythree are shown in FIG. 5 to avoid overcomplicating the drawing. Inaddition, each user may utilize more than one type of conferencingdevice and also more than one of each type of conferencing device.

Conferencing devices 502, 505, 506 may be coupled to communicationnetwork 504. Communication network 504 may be one or more networksincluding the Internet, a mobile phone network, mobile voice or datanetwork (e.g., a 4G or LTE network), cable network, public switchedtelephone network, or other types of communications network orcombinations of communications networks. Conferencing server 508, andconferencing devices 502, 505, 506 may be coupled to communications path504 via one or more communications paths, such as a satellite path, afiber-optic path, a cable path, a path that supports Internetcommunications (e.g., IPTV), free-space connections (e.g., for broadcastor other wireless signals), or any other suitable wired or wirelesscommunications path or combination of such paths.

Although communications paths are not drawn between conferencing devices502, 505, 506, and conferencing server 508, these devices maycommunicate directly with each other via communications paths, such asshort-range point-to-point communications paths, such as USB cables,IEEE 1394 cables, wireless paths (e.g., Bluetooth, infrared, IEEE802-11x, etc.), or other short-range communication via wired or wirelesspaths. BLUETOOTH is a certification mark owned by Bluetooth SIG, INC.The conferencing devices may also communicate with each other through anindirect path via communication network 504.

Conferencing applications may be, for example, stand-alone applicationsimplemented on conferencing devices. For example, the conferencingapplication may be implemented as software or a set of executableinstructions, which may be stored in storage 408 and executed by controlcircuitry 404 of a conferencing device 502, 505, 506. In someembodiments, conferencing systems may be client-server applicationswhere only a client application resides on the conferencing device, anda server application resides on conferencing server 508. For example,conferencing systems may be implemented partially as a clientapplication on control circuitry 404 of conferencing devices 502, 505,506 and partially on conferencing server 508 as a server applicationrunning on control circuitry of conferencing server 508. When executedby control circuitry of conferencing server 508, the conferencingapplication may instruct the control circuitry to capture audio,generate audio signatures (e.g., based on captured audio), join a deviceto the conference, and generate the conferencing system output (e.g., avideo feed of the conference, audio feed of the conference, text chat orother functionalities for the conference, etc.) and transmit aconference ID (e.g., to a device newly joined to a conference) and thegenerated output to conferencing devices 502, 505, 506. The clientapplication may instruct control circuitry of the receiving conferencingdevices 502, 505, 506 to generate the conferencing system output.

Conferencing devices 502, 505, 506 may operate in a cloud computingenvironment to access cloud services. In a cloud computing environment,various types of computing services for content sharing, storage ordistribution (e.g., video sharing sites or social networking sites) areprovided by a collection of network-accessible computing and storageresources, referred to as “the cloud.” Cloud resources may be accessedby conferencing device 502, 505, 506 using, for example, a web browser,a conferencing system, a desktop application, a mobile application,and/or any combination of access applications of the same. Conferencingdevices 502, 505, 506 may be a cloud client that relies on cloudcomputing for application delivery, or the conferencing device may havesome functionality without access to cloud resources. For example, someapplications running on conferencing device 502, 505, 506 may be cloudapplications, i.e., applications delivered as a service over theInternet, while other applications may be stored and run on theconferencing device. In some embodiments, a user device may receivecontent from multiple cloud resources simultaneously. For example, auser device can stream audio from one cloud resource while downloadingcontent from a second cloud resource. Or a user device can downloadcontent from multiple cloud resources for more efficient downloading. Insome embodiments, conferencing devices can use cloud resources forprocessing operations such as the processing operations performed byprocessing circuitry described in relation to FIG. 4.

FIG. 6 shows a processing flow 600 for joining device 601 to aconference, in accordance with some embodiments of this disclosure. Itshould be noted that process 600 or any step thereof could be performedon, or provided by, any of the devices shown in FIGS. 4-5. For example,process 600 may be executed by devices 502, 505, 506 (e.g., via controlcircuitry 404) and/or control circuitry of conferencing server 508, asinstructed by a conferencing application that may be implemented onconferencing device 502, and/or conferencing device 505 and/orconferencing device 506 and/or conferencing server 508, such as todistribute control of database management application operations for atarget device among multiple devices. In addition, one or more steps ofprocess 600 may be incorporated into or combined with one or more stepsof any other process or embodiment (e.g., process 700 of FIG. 7).

At 602, control circuitry of a conferencing server 603 (e.g., server 508of FIG. 5) may establish a conference (e.g., conference 105 of FIG. 1,conference 301 of FIG. 3) via a communication network (e.g., network 504of FIG. 5). For example, conferencing server 603 may communicate withusers via one or more devices 605 (e.g., devices 502, 505, 506 of FIG.5) to set up the conference. In some embodiments, at least one of suchusers may be physically present in a conference room (e.g., conferenceroom 300 of FIG. 3). The conference may include multiple participantsfrom several different physical locations, and at any of such locationsthere may be a single user or multiple users present (e.g.,communicating via a single device, such as device 302 of FIG. 3, in aconference room, or communicating via multiple devices). The conferencemay be associated with a unique conference ID stored at conferencingserver 603, and such conference ID may be communicated to each ofdevices 605 to enable the devices 605 to join the conference.

At 604, a microphone of each of one or more devices (e.g., devices 502,505, 506 of FIG. 5) joined to the conference may capture audio signalsof voices of users in the conference. The captured audio signals (e.g.,audio input 202 of FIG. 2) may be sampled at regular intervals (e.g.,periods of 1-2 seconds with samples taken every few milliseconds duringthe period). In some embodiments, the microphone may pick up ambientsounds (e.g., voices of users in the same physical location as themicrophone, voices of users joined to the conference in a differentphysical location, background noise, music, etc.) and certainfrequencies or noise may be filtered from the signal (e.g., usingdigital signal processor 206 of FIG. 2 and/or control circuitry of thedevices 605 or conferencing server 603). For example, noise or otherbackground sounds may be removed from the signal, and/or only voices ofusers in the same room as the microphone may be included in the signal(e.g., only voices above a threshold amplitude may be included in thesignal, since volume of the voice may be louder in the same physicallocation than over a network). An analog filter (e.g., to block signalsnot within a frequency of the human voice) or digital filter (e.g., byapplying an algorithm to a sequence of digital samples) may be employed.

At 606, the captured audio signals may be transmitted to conferencingserver 603. In some embodiments, the captured audio signal may betransmitted from each of the devices 605 joined to the conference at thesame time, or at various predetermined times. The captured audio signalsmay be transmitted to conferencing server 603 each time the audio issampled by the respective devices.

At 608, control circuitry of conferencing server 603 (and/or digitalsignal processor 206 of FIG. 2) may generate audio signatures based onthe audio signals (e.g., received via I/O path 402 of FIG. 4), such asin accordance with the techniques discussed in connection with FIG. 2.For example, audio modulations of the received signals may be compressedinto audio signatures. Various digital signal processing algorithms maybe used (e.g., fast Fourier transform) in generating the audiosignatures. In some embodiments, the audio can be converted totranscribed text (e.g., using ASR and/or speech-to-text circuitry) andsuch transcribed text may be used as an audio signature. The audiosignature may be generated for each audio signal received byconferencing server 603 from the devices 605 joined to the conference,and audio signals may be transmitted to the server (e.g., atpredetermined times, for the purposes of generating audio signatures)until the conclusion of the conference.

At 610, control circuitry of conferencing server 603 (e.g., server 508of FIG. 5) may store (e.g., in storage 408 of FIG. 4) the generatedaudio signatures in connection with the conference ID associated withthe conference. In addition to the conference ID, the generatedsignatures may be associated and/or tabulated with device IDsrespectively associated with devices 605 joined to the conference, and atimestamp associated with each audio signature. In some embodiments,conferencing server 603 maintains this tabulated data (e.g., in cache orbuffer memory) such that the control circuitry of conferencing server603 can retrieve the recently generated audio signatures more quicklythan audio signatures generated at an earlier time. It should be notedthat conferencing server 603 may store any number of conference IDs forvarious ongoing conferences (e.g., within particular organizations,across multiple organizations, etc.).

At 612, control circuitry (e.g., control circuitry 404 of device 400 or401 of FIG. 4) may determine that a user (e.g., user 310 of FIG. 3)associated with a device 601 (and not yet joined to the conference) hasphysically entered a conference room in which one or more devices (amongdevices 605) are joined to a conference established by the conferencingsystem. For example, techniques discussed in connection with FIG. 3 maybe employed to make such a determination. In some embodiments, thedevice (e.g., device 311 of FIG. 3) may periodically transmit (e.g., asa push notification or a pull notification) its current location (e.g.,GPS coordinates) to conferencing server 603. The control circuitry ofconferencing server 603 may compare such location to the locationsand/or IP addresses of one or more devices 605 joined to the conferenceto determine whether device 601 not yet joined to the conference is inthe same physical location (e.g., conference room) as another device(among devices 605) joined to the conference.

At 614, upon the control circuitry of device 601 determining that suchdevice is located in the same physical location as one or more devices605 joined to a conference currently being hosted by conferencing server603, the conferencing application causes a microphone (e.g., microphone113 of FIG. 1) of device 601 to start capturing ambient sound. In someembodiments, the microphone may capture voices from participants in thesame physical location as the user and voices of conference participantslocated in different locations. The microphone of device 601 may captureaudio as described in 604 of FIG. 6.

At 616, device 601 may transmit (e.g., via I/O path 402 of FIG. 4) thecaptured ambient audio signal to conferencing server 603. In someembodiments, device 601 may transmit multiple audio signals to theconferencing server at regular intervals.

At 618, conferencing server 603 may generate an audio signature based onthe audio signal received from device 601. The audio signal may begenerated in a similar manner to that of 608 of FIG. 6.

At 620, control circuitry of conferencing server 603 may compare theaudio signature, generated based on the audio signal received fromdevice 601, to the audio signatures stored at conferencing server 603.In some embodiments, the comparison may be performed by controlcircuitry (e.g., control circuitry 404) at both conferencing server 603and locally at device 601. As another example, the audio signatures maybe stored locally at device 601, or retrieved via a network (e.g.,network 504 of FIG. 5) from the conferencing server for comparison atdevice 601. In some embodiments, the conferencing server may retrievethe recently stored audio signatures for comparison at the outset of thecomparison process, as such audio signatures may be stored in cache orbuffer memory for fast retrieval (and may be more likely to have beengenerated in an ongoing conference).

In some embodiments, the control circuitry compares audio features orcharacteristics of the generated audio signature to audio features orcharacteristics of the stored audio signatures (e.g., a base orfundamental frequency of a voice, modulation, amplitude, or other audiocharacteristics). For example, conferencing server 603 (e.g., usingdigital signal processor 206 and/or control circuitry) may extract afirst peak point with a first frequency and first average power from afirst spectrogram of the generated audio signature, and extract a secondpeak point with a second frequency and second average power from asecond spectrogram of a stored audio signature. Conferencing server 603may determine a frequency difference value between the first frequencyand the second frequency and a power difference value between the firstaverage power and the second average power. Based on the comparing,conferencing server 603 may determine whether the generated audiosignature matches any of the stored audio signatures. For example, thegenerated audio signature may be determined to match a stored audiosignature if the frequency difference value is under a first threshold(e.g., 100 Hz) and the power difference value is under a secondthreshold (e.g., 20 dB). In some embodiments, conferencing server 603may compare respective features vectors which may constitute the audiosignature, and determine a match based on whether a similarity betweensuch features vectors is within a certain threshold.

In some embodiments, the comparison between the generated audiosignature received from device 601 and the stored audio signatures mayinclude audio analysis techniques to determine whether there is matchbetween voices of particular users (e.g., frequency analysis todetermine a base frequency and unique harmonic pattern of a particularvoice, phoneme analysis to determine an accent of a particular voice,etc.). For example, the control circuitry may determine that there is amatch if a similarity score computed by the control circuitry exceeds apredetermined threshold. Phoneme analysis is described in greater detailin Mehra, U.S. Pat. No. 10,621,970, issued Apr. 14, 2020, andVenkataraman et al., U.S. Pat. No. 10,324,940, issued Jun. 18, 2019,which are hereby incorporated by reference herein in their entireties.

At 622, the control circuitry (e.g., of conferencing server 508 of FIG.5) may determine that there is a match between the audio signaturegenerated based on the audio signal transmitted by device 601 and one ormore of the audio signatures transmitted at 606. For example, certainaudio characteristics between the audio signatures may be sufficientlysimilar (e.g., within a certain threshold, such as after weighting andnormalizing is performed) to each other to determine that there is amatch. In some embodiments, the control circuitry may determine thatthere is not a match with audio signatures related to other ongoingconferences prior to determining the matched conference (e.g.,conference 105 of FIG. 1. Upon determining that there is a match, thecontrol circuitry of conferencing server 603 may transmit the conferenceID associated with the conference to device 601.

At 624, device 601 may be automatically joined to the ongoing conferenceusing the conference ID received from conferencing server 603. In someembodiments, the user may be automatically joined to the conference(e.g., without further user input). As another example, the controlcircuitry may generate for presentation a selectable prompt to join theconference, and the user may be joined to the conference when selectionof the prompt is received.

At 626, since there may be other devices in the same physical conferenceroom as the user associated with device 601, the microphone and/orspeakers and/or video feed of device 601 may be automatically mutedand/or disabled (e.g., without further user input) in order to avoidaudio feedback. An icon (e.g., indicator 312 of FIG. 3 or other indicia)associated with user 601 may be generated (e.g., by control circuitry404 of FIG. 4 of the device associated with the user or conferencingserver 603) for presentation on a display (e.g., projector 304 of FIG.3) to indicate to other conference participants that the user is nowparticipating in the conference (e.g., via devices 605 in the physicalconference room already joined to the conference). Accordingly,irritating audio feedback can be minimized or avoided, and the user mayconveniently join the ongoing conference, while the system makes theother participants aware that the user has joined the conference. Insome embodiments, upon the user joining the conference, varioussupplemental features may be made available (e.g., screensharingcapabilities, text or chat capabilities, etc.).

FIG. 7 shows a processing flow 700 for joining device 701 to aconference, in accordance with some embodiments of this disclosure. Itshould be noted that process 700 or any step thereof could be performedon, or provided by, any of the devices shown in FIGS. 4-5. For example,process 700 may be executed by devices 502, 505, 506 of FIG. 5 (e.g.,via control circuitry 404) and/or control circuitry of conferencingserver 508, as instructed by a conferencing application that may beimplemented on conferencing device 502, and/or conferencing device 505and/or conferencing device 506 and/or conferencing server 508, such asto distribute control of database management application operations fora target device among multiple devices. In addition, one or more stepsof process 700 may be incorporated into or combined with one or moresteps of any other process or embodiment (e.g., process 600 of FIG. 6).

At 702, conferencing server 703 may establish a conference via acommunication network (e.g., communication network 504 of FIG. 5) in asimilar manner to that of 602 of FIG. 6. At 704, a microphone of each ofdevices 705 joined to the conference may capture audio signals of voicesof users in the conference, in a similar manner to 604 of FIG. 6.

At 706, one or more devices 705 (e.g., devices 502, 505, 506 of FIG. 5)joined to the conference may generate (e.g., via control circuitry 404of FIG. 4) respective audio signatures based on the audio signalscaptured at the respective devices 705. Each of the devices 705 maygenerate the audio signatures in a similar manner to that of 608 of FIG.6, and in accordance with the techniques discussed in connection withFIG. 2.

At 708, each of devices 705 may transmit (e.g., via I/O path 402 of FIG.4) the generated audio signatures to conferencing server 703. In someembodiments, the generated audio signatures may be transmitted from eachof the devices 705 joined to the conference at the same time, or atstaggered times. For example, the generated audio signatures may betransmitted to conferencing server 703 each time the audio is sampled bythe respective devices 705 (e.g., upon completion of generation of theaudio signatures).

At 710, conferencing server 703 may receive (e.g., via I/O path 402 ofFIG. 4) the generated audio signatures, and control circuitry of theconferencing server (e.g., server 508 of FIG. 5) may store (e.g., instorage 408 of FIG. 4) the generated audio signatures in connection withthe conference ID associated with the conference. In addition to theconference ID, the generated signatures may be associated and/ortabulated with device IDs respectively associated with devices 705joined to the conference, and a timestamp associated with each audiosignature. In some embodiments, conferencing server 703 maintains thistabulated data (e.g., in cache or buffer memory) such that the controlcircuitry of conferencing server 703 can retrieve the recently generatedaudio signatures more quickly than audio signatures generated at anearlier time. It should be noted that conferencing server 703 may storeany number of conference IDs for various ongoing conferences (e.g.,within particular organizations, across multiple organizations, etc.).

At 712, control circuitry (e.g., control circuitry 404 of device 400 or401 of FIG. 4) may determine that a user (e.g., user 311 of FIG. 3)associated with device 701 has physically entered a conference room inwhich one or more devices are joined to a conference established by theconferencing system. For example, techniques discussed in connectionwith FIG. 3 may be employed to make such a determination, and in asimilar manner to that of 612 of FIG. 6.

At 714, upon control circuitry (e.g., control circuitry 404 of FIG. 4)of the device 701 determining that such device is located in the samephysical location as one or more devices joined to a conferencecurrently being hosted by conferencing server 703, the conferencingapplication causes a microphone (e.g., microphone 113 of FIG. 1) of thedevice to start capturing ambient sound. In some embodiments, themicrophone may capture voices from participants in the same physicallocation as the user and voices of conference participants located indifferent locations. The microphone of the device may capture audio asdescribed in connection with 604 of FIG. 6.

At 716, the device 701 may generate (e.g., via control circuitry 404 ofFIG. 4) one or more audio signatures based on the audio signals capturedat the device. Such device may generate the audio signatures in asimilar manner to 608 of FIG. 6, and such as in accordance with thetechniques discussed in connection with FIG. 2.

At 718, the device may transmit (e.g., via I/O path 402 of FIG. 4) thegenerated audio signature to conferencing server 703. In someembodiments, the device may transmit multiple audio signals toconferencing server 703 at regular intervals.

At 720, control circuitry (e.g., of the conferencing server) may compareone or more audio signatures received from the device 701 to the audiosignatures stored at the conferencing server. Such comparison may beperformed in a similar manner to 620 of FIG. 6.

At 722, the control circuitry (e.g., of conferencing server 508 of FIG.5) may determine that there is a match between the audio signaturegenerated by the device 701 and the audio signatures generated by thedevices already joined to the conference (e.g., conference 301 of FIG.3). Upon determining that there is a match, the control circuitry ofconferencing server 703 may transmit the conference ID associated withthe conference to the device 701.

At 724, the device 701 may be automatically joined to the ongoingconference using the conference ID received from conferencing server703. In some embodiments, the user may be automatically joined to theconference (e.g., without further user input). As another example, thecontrol circuitry may generate for presentation a selectable prompt tojoin the conference, and the user may be joined to the conference whenselection of the prompt is received.

At 726, since there may be other devices (among devices 705) in the samephysical conference room as the user associated with device 701 nowjoined to the conference, the microphone and/or speakers and/or videofeed of such device may be automatically muted and/or disabled (e.g.,without further user input) in order to avoid audio feedback. An icon(e.g., indicator 312 or other indicia) associated with the user may begenerated (e.g., by control circuitry 404 of the device 701 orconferencing server 703) for presentation on a display (e.g., projector304 of FIG. 3) to indicate to other conference participants that theuser is now participating in the conference (e.g., via a device in thephysical conference room already joined to the conference). Accordingly,irritating audio feedback can be minimized or avoided, and the user mayconveniently join the ongoing conference, while the system makes theother participants aware that the user has joined the conference. Insome embodiments, upon the user joining the conference, varioussupplemental features may be made available (e.g., screenshare, meetingchat, etc.).

Those of skill in the art would appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the embodiments disclosed herein may be implemented withelectronic hardware, computer software, or combinations of both. Toillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software may depend upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present invention. Moreover, method steps may beinterchanged without departing from the scope of the invention.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield-programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general purpose processor may be a microprocessor, but in thealternative, the processor as described herein may be any conventionalprocessor, controller, microcontroller, or state machine. A processoralso may be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

The steps of a method or algorithm described in connection with theembodiments disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium may be coupled to the processor such that theprocessor reads information from, and writes information to, the storagemedium. In the alternative, the storage medium may be integral to theprocessor. The processor and the storage medium may reside in an ASIC.The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal.

Various modifications to these embodiments will be readily apparent tothose skilled in the art, and the generic principles defined herein maybe applied to other embodiments without departing from the spirit orscope of the invention. Thus, the present invention is not intended tobe limited to the embodiments shown herein but is to be accorded thewidest scope consistent with the principles and novel features disclosedherein. Thus, one of ordinary skill in the art would understand that theinvention is not to be limited by the foregoing illustrative details,but rather is to be defined by the appended claims.

1. A method comprising: generating, by a conferencing server, a firstaudio signature based on voices of a plurality of users in a conference;storing the first audio signature; receiving, by the conferencingserver, an audio signal captured by a microphone of a device associatedwith a first user, wherein the device is not joined to the conference;generating, by the conferencing server, a second audio signature basedon the received audio signal; comparing the first audio signaturegenerated based on the voices of the plurality of users in theconference to the second audio signature generated based on the audiosignal captured by the microphone of the device associated with thefirst user when the device is not joined to the conference; and inresponse to determining that first audio signature matches the secondaudio signature, joining the device associated with the first user tothe conference.
 2. The method of claim 1, wherein the audio signalcaptured by the microphone of the device associated with the first usercomprises at least one of the voices of the plurality of users in theconference.
 3. The method of claim 2, further comprising: determiningwhether the device associated with the first user is in a same physicallocation as a device associated with at least one user of the pluralityof users in the conference; and wherein the audio signal is captured bythe microphone of the device associated with the first user in responseto determining that the device associated with the first user is in thesame physical location as the device associated with the at least oneuser.
 4. The method of claim 1, wherein joining the device associatedwith the first user to the conference comprises generating forpresentation an icon indicating to each user joined to the conferencethat the first user is joined to the conference.
 5. The method of claim1, further comprising: after joining the device associated with thefirst user to the conference, causing the microphone and a speaker ofthe device associated with the first user to be automatically mutedwithout receiving a user command to mute the microphone and the speaker.6. The method of claim 1, further comprising: assigning, by theconferencing server, a conference identifier to the conference, whereinthe first audio signature is associated with the conference identifier;wherein joining the device associated with the first user to theconference comprises transmitting the conference identifier to thedevice associated with the first user.
 7. The method of claim 1, whereinthe first audio signature and the second audio signature are generatedby sampling the voices of the plurality of users in the conference andthe audio signal captured by the microphone, respectively, at regularintervals.
 8. The method of claim 1, wherein the first audio signatureand the second audio signature are generated by transcribing the voicesof the plurality of users in the conference and the audio signalcaptured by the microphone, respectively, into text.
 9. A systemcomprising: control circuitry configured to: generate a first audiosignature based on voices of a plurality of users in a conference;storage circuitry configured to: store the first audio signature;input-output (I/O) circuitry configured to: receive an audio signalcaptured by a microphone of a device associated with a first user,wherein the device is not joined to the conference; and the controlcircuitry is further configured to: generate a second audio signaturebased on the received audio signal; compare the first audio signaturegenerated based on the voices of the plurality of users in theconference to the second audio signature generated based on the audiosignal captured by the microphone of the device associated with thefirst user when the device is not joined to the conference; and inresponse to determining that first audio signature matches the secondaudio signature, join the device associated with the first user to theconference.
 10. The system of claim 9, wherein the audio signal capturedby the microphone of the device associated with the first user comprisesat least one of the voices of the plurality of users in the conference.11. The system of claim 10, wherein the control circuitry is furtherconfigured to: determine whether the device associated with the firstuser is in a same physical location as a device associated with at leastone user of the plurality of users in the conference; and wherein theaudio signal is captured by the microphone of the device associated withthe first user in response to determining that the device associatedwith the first user is in the same physical location as the deviceassociated with the at least one user.
 12. The system of claim 9,wherein in joining the device associated with the first user to theconference, the control circuitry is further configured to generate forpresentation an icon indicating to each user joined to the conferencethat the first user is joined to the conference.
 13. The system of claim9, wherein the control circuitry is further configured to: after joiningthe device associated with the first user to the conference, cause themicrophone and a speaker of the device associated with the first user tobe automatically muted without receiving a user command to mute themicrophone and the speaker.
 14. The system of claim 9, wherein thecontrol circuitry is further configured to: assign a conferenceidentifier to the conference, wherein the first audio signature isassociated with the conference identifier; wherein in joining the deviceassociated with the first user to the conference, the control circuitryis further configured to transmit the conference identifier to thedevice associated with the first user.
 15. The system of claim 9,wherein the control circuitry is configured to, in generating the firstaudio signature and the second audio signature, sample the voices of theplurality of users in the conference and the audio signal captured bythe microphone, respectively, at regular intervals.
 16. The system ofclaim 9, wherein the control circuitry is configured to, in generatingthe first audio signature and the second audio signature, transcribe thevoices of the plurality of users in the conference and the audio signalcaptured by the microphone, respectively, into text.
 17. A methodcomprising: generating a first audio signature based on voices of aplurality of users in a conference; storing the first audio signature;receiving, by a conferencing server, a second audio signature, wherein:the second audio signature was generated by a device associated with afirst user based on an audio signal captured by a microphone of thedevice associated with the first user when the device associated withthe first user was not joined to the conference; comparing the firstsignature generated based on the voices of the plurality of users in theconference and stored by the conferencing server to the received secondaudio signature generated based on the audio signal captured by themicrophone of the device associated with the first user when the deviceis not joined to the conference; and in response to determining thatfirst audio signature matches the second audio signature, joining thedevice associated with the first user to the conference.
 18. The methodof claim 17, wherein the audio signal captured by the microphone of thedevice associated with the first user comprises at least one of thevoices of the plurality of users in the conference.
 19. The method ofclaim 18, further comprising: determining whether the device associatedwith the first user is in a same physical location as a deviceassociated with at least one user of the plurality of users in theconference; and wherein the audio signal is captured by the microphoneof the device associated with the first user in response to determiningthat the device associated with the first user is in the same physicallocation as the device associated with the at least one user.
 20. Themethod of claim 17, further comprising: after joining the deviceassociated with the first user to the conference, causing the microphoneand a speaker of the device associated with the first user to beautomatically muted without receiving a user command to mute themicrophone and the speaker. 21.-30. (canceled)